change volume to named volume rather than host bind mount (#275) - #276
Merged
Merged
Conversation
sarahmccuan
marked this pull request as draft
August 22, 2026 22:38
sarahmccuan
marked this pull request as ready for review
August 22, 2026 22:39
Owner
|
Good investigation, if that is the cause, the fix is more than welcome! |
HugoFara
added
bug
Author
|
Confirmed that it worked locally on windows anyway. Would probably be worth someone testing on a linux box to make sure nothing breaks on that side. |
Owner
|
I have launched the workflows, and I'll test on Linux when I get the time, thanks for the PR! N. B.: I also found the lone |
HugoFara
added a commit
that referenced
this pull request
Aug 27, 2026
A minor bump rather than a patch: the release adds four-grade FSRS review and scheduled Anki export, makes the language parser setting real, and drops three columns from `words`. Condense the changelog entries, which had grown to full explanations of each mechanism, down to what a reader upgrading needs to know. The reasoning stays in the commits and pull requests it came from. Add the entry for #276, which had none: moving the database to a named Docker volume is the change in this release most likely to alarm someone, since an existing install looks empty until the old data is imported. ParseCoverage carried @SInCE 3.4.3, the only version guess in the new code.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixing all the migration failures: errno 150/194 and "error 41" migration failures in #275.
Root cause: docker-compose.yml bind-mounted the MariaDB data directory from the Windows host (./lwt_db_data:/var/lib/mysql); that path is case-insensitive, so MariaDB force-set lower_case_table_names=2 (unsupported on Linux builds) and every ALTER TABLE failed to rename its tablespace, which cascaded into the errors.
Fix: Switched that mount to a named Docker volume (lwt_db_data:/var/lib/mysql) so the InnoDB files live on ext4 inside the Docker VM.